fix: bracket match query display#7796
Conversation
📝 WalkthroughWalkthroughThe ChangesMatchQuery display formatting
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
2c5f0f9 to
39ac6d5
Compare
wjones127
left a comment
There was a problem hiding this comment.
This seems inconsistent with existing nodes. You mention that this fixes the metrics output, but there's no example in the PR description nor the unit tests, so it's hard to me to evaluate that.
| "AggregateExec: mode=Single, gby=[], aggr=[count(Int32(1))] | ||
| MatchQuery: column=text, query=document", | ||
| [MatchQuery: column=text, query=document]", |
There was a problem hiding this comment.
issue(blocking): This looks inconsistent with other nodes, which wrap arguments in brackets, not the whole line. See AggregateExec above. Should we wrap the query argument instead?
There was a problem hiding this comment.
Updated to wrap only the query argument, matching the existing argument-bracketing style: MatchQuery: column=text, query=[document].
39ac6d5 to
b90e528
Compare
Wrap the
MatchQueryquery argument in brackets so metric suffixes do not look like part of the query term.Example verbose metrics output changes from:
to:
Summary by CodeRabbit
Style
MatchQueryto show the query value in square brackets (e.g.,query=[...]) for the default/verbose formats.Tests
MatchQuerybracketed formatting across legacy and non-legacy scenarios.